Data replication from a cloud-based storage resource

ABSTRACT

A local computing device replicates data stored in a cloud-based storage resource in a way that is substantially transparent to end users. A counter generation module provides a source for sequentially increasing counter indices, each of which is associated with a creation timestamp. When a data record managed by the cloud-based storage resource is created, updated or deleted, an address of the modified data record is recorded in a journal, along with unique counter index and timestamp values. Later, when data records stored in the cloud-based storage resource are to be replicated at the local computing device, data records corresponding to the sequential counter indices listed in the journal are sent to the local computing device. Only those data records which correspond to blocks of uninterrupted sequential counter indices are transmitted to the local computing device, thereby ensuring consistency of the replicated data.

REFERENCE TO PRIOR APPLICATION

This application claims the benefit of U.S. Provisional PatentApplication 62/110,807 (filed 2 Feb. 2015). The entire disclosure ofthis priority application is hereby incorporated by reference herein.

FIELD OF THE INVENTION

This application relates generally to data management systems, and morespecifically to methods that enable a local computing device toreplicate data stored in a cloud-based storage resource.

BACKGROUND

As digital computing systems become increasingly ubiquitous, the datastorage demands associated with such systems continue to growgeometrically. One way of addressing this ever-expanding storage demandis through the use of cloud-based storage resources. In general, acloud-based storage resource can be understood as providing data storagein a distributed network of storage devices rather than on one specificdevice. Storing data in a cloud-based storage resource, which is oftencolloquially referred to as storing data “in the cloud”, enables thestored data to be accessed via nearly any device capable of connectingto the resource. Cloud-based storage resources therefore provide userswith a convenient and scalable storage solution that eliminates the needto procure and maintain dedicated physical storage hardware. Storingdata in the cloud also provides a convenient way to share data amongstmultiple users, thus facilitating workgroup collaboration. Cloud-basedstorage resources are also often used to replicate storage provided at alocal computing device, for example to provide a backup copy of a localfile system. Maintaining synchronization of local and cloud-based filesystems is particularly important in data replication applicationsbecause the benefit of a data replication scheme decreases as the numberof discrepancies between the local and cloud-based file systemsincreases. As a result, a number of data synchronization schemes havebeen developed to address the challenge of minimizing suchdiscrepancies.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram schematically illustrating selected componentsof an example embodiment of a data replication system that enables alocal computing device to replicate data stored in a cloud-based storageresource that is managed by a cloud storage gateway.

FIGS. 2A and 2B comprise a flowchart illustrating an example datastorage method that maintains a sequential counter log having a counterindex and a timestamp for each of a plurality of users. The entries inthe counter log correspond to journal records that, in turn, correspondto updates to data records that are stored in a cloud-based storageresource that is managed by a cloud storage gateway.

FIGS. 3A through 3D comprise a flowchart illustrating an example datareplication method that allows a local computing device to replicatedata stored in a cloud-based storage resource that is managed by a cloudstorage gateway.

DETAILED DESCRIPTION

The easily accessible and scalable nature of cloud-based storageresources provides an attractive solution for data backup, retention,and replication applications. For example, a user may wish tosynchronize local and cloud file systems such that changes made to afile locally are automatically reflected in the cloud-based version ofthat same file, and vice-versa. This not only provides redundancy in theevent the local file system fails or is otherwise compromised, but italso ensures that the local file system reflects changes made in thecloud-based storage resource. This is particularly useful incollaboration applications, where a local user may be unaware of changesmade to digital assets stored in the cloud. Ideally, data replication ismaintained continually, thus reducing the number of discrepancies thatexist between the local and cloud file systems. A robust datareplication system should also continue to operate at the same time endusers are accessing and manipulating the stored data, and thereforeshould not be adversely affected by data that is temporarily unavailableat a given time. Furthermore, from an end user's perspective, a datareplication system should operate transparently and should not consumesignificant processing resources. Given these user expectations, theburden involved in maintaining accurate synchronization between localand cloud file systems can be significant. Providing a system that meetsthese performance criteria and user expectations represents asubstantial challenge in the field of cloud-based data management.

Thus, and in accordance with certain of the embodiments disclosedherein, improved data management techniques enable a local computingdevice to robustly replicate data stored in a cloud-based storageresource in a way that is substantially transparent to end users. In oneimplementation a counter generation module provides a source forsequentially increasing counter indices, each of which is associatedwith a creation timestamp. When a data record stored in the cloud-basedstorage resource is created, updated, or deleted, an address of theupdated data record is recorded in a corresponding journal record, alongwith unique counter index and timestamp values. Later, when data recordsstored in the cloud-based storage resource are to be replicated at thelocal computing device, for example in response to a threshold number ofdata manipulation operations having occurred, or a predetermined timeperiod having elapsed, data records corresponding to sequential counterindices listed in the journal are sent to the local computing device.Only those data records which correspond to blocks of uninterruptedsequential counter indices are transmitted to the local computingdevice, thereby ensuring consistency of the replicated data. Where thesequence of counter indices is interrupted or broken, and where suchinterruption persists beyond a threshold time limit, it is assumed thatan inconsistency exists in the journal, for example as may be caused bya failed data write operation or a failed storage device in thecloud-based storage resource. In such case a full synchronization can beperformed between the local computing device and the cloud-based storageresource. Numerous configurations and modifications will be apparent inlight of this disclosure.

Certain of the embodiments disclosed herein provide a system that isable to robustly and accurately replicate a cloud-based file system at alocal computing device in a way that is substantially transparent to endusers, and that does not consume significant processing resources. Thesequential indices procured by counter generation module form the basisof the aforementioned journal. Gaps in the indices recorded in thejournal, and inconsistencies between the indices generated by thecounter and the indices recorded in the journal are indicative of datarecords which are unavailable. Such data records may be unavailablebecause of other concurrent data manipulation operations, because of ahardware failure in the cloud-based storage resource, or because of aproblem in the counter generation module. Regardless of the cause, thevarious data replication methods disclosed herein provide a robust wayof detecting such gaps and inconsistencies, and therefore allowalternative procedures for replicating data corresponding to such gapsand inconsistencies to be invoked. Yet another advantage associated withcertain of the techniques disclosed herein is that such techniquesreduce the extent to which read state information is persisted at alocal computing device. In particular, only a single read state indexrepresenting the next data record to be replicated is stored at thelocal computing device, thus reducing the extent to which localcomputing resources are dedicated to data replication. These and otheradvantages will be apparent in view of the foregoing detaileddescription.

As used herein, the term “cloud-based storage resource” refers, inaddition to its ordinary meaning, to a computing resource that providesdata storage in a distributed network of storage devices rather than onespecific device. However, notwithstanding the fact that it comprises alarge number of distributed resources, a cloud-based storage resourceacts as—and therefore can be interacted with as—a single storage device.The data stored in a cloud-based storage resource can be logicallyorganized into a plurality of “data records” which may, for example,correspond to individual files, objects, or other logical containers.Cloud-based storage resources are typically owned and administered by ahost that is responsible for keeping data available and accessible,although larger organizational users may build and administer their owncloud-based storage resources. Regardless of the particularadministrative model implemented, users access the services provided bya cloud-based storage resource via an application programming interface(API) or via applications that use the API, such as a cloud storagedesktop application, a cloud service gateway, or a web-based contentmanagement system. In many cases the same host that manages thecloud-based storage resource also provides the API or user interfacethrough which the resource can be leveraged. Cloud-based storageresources are therefore often understood as being implemented in aclient-server computing environment, wherein the cloud-based storageresource functions as a server, and the local computing device acts as aclient. Commercially available cloud-based storage resources includeGoogle Drive (Google Inc., Mountain View, Calif.), iCloud (Apple Inc.,Cupertino, Calif.), and OneDrive (Microsoft Corporation, Redmond,Wash.).

As used herein, the term “data structure” refers, in addition to itsordinary meaning, to a way of storing and organizing data in a computeraccessible memory so the data can be used by an application or softwaremodule. In its simplest form, a data structure can be, for example, aset of one or more memory locations. In some cases a data structure maybe implemented as a so-called record, sometimes referred to as a structor tuple, and may have any appropriate number of fields, elements, orstorage locations. As will be further appreciated, a data structure mayinclude data of interest or a pointer that refers to a memory locationwhere the data of interest can be found. A data structure may have anyappropriate format such as, for example, a lookup table or index format;an array format; a hash table format; a graph, tree, or hierarchicalformat having a number of nodes; an object format that includes datafields; or a combination of the foregoing. A data structure may includeexecutable code for accessing and modifying the underlying structure andformat of the data stored therein. In a more general sense, the datastructure may be implemented as a data set that can store specificvalues without being constrained to any particular order or format. Inone embodiment, a data structure comprises a table correlating aparticular counter index, timestamp, and network address in acloud-based storage resource. Numerous other data structure formats andapplications will be apparent in light of this disclosure.

System Architecture

FIG. 1 is a block diagram schematically illustrating selected componentsof an example embodiment of a data replication system 1000 that enablesa local computing device 100 to replicate data stored in a cloud-basedstorage resource that is managed by, for example, a cloud storagegateway 300. In such embodiments local computing device 100 and cloudstorage gateway 300 communicate with each other via a network 500. Cloudstorage gateway 300 is also configured to communicate with a countergeneration module 200 via network 500. Other embodiments may have feweror more communication paths, networks, subcomponents, and/or resourcesdepending on the granularity of a particular implementation. Forexample, in an alternative embodiment counter generation module 200 isintegrated into and provided by cloud storage gateway 300. Likewise,while one local computing device and one cloud storage gateway areillustrated in FIG. 1 for clarity, it will be appreciated that, ingeneral, tens, hundreds, thousands, or more cloud storage gateways canbe configured to service the storage needs of an even larger number oflocal computing devices. Thus the embodiments described and illustratedherein are not intended to be limited to the provision or exclusion ofany particular services and/or resources.

Local computing device 100 may comprise, for example, one or moredevices selected from a desktop computer, a laptop computer, aworkstation, an enterprise-class server computer, a handheld computer, atablet computer, a cellular telephone, a smartphone, a set-top box, orany other suitable computing device. A combination of different devicesmay be used in certain embodiments. Local computing device 100 includesone or more software modules configured to implement certain of thefunctionalities disclosed herein, as well as hardware capable ofenabling such implementation. The hardware may include, but is notlimited to, a processor 110, a memory 120, and a communication module140. A bus and/or interconnect 190 is also provided to allow for inter-and intra-device communications using, for example, communication module140. The hardware may also include integrated or peripheral input/outputcomponents such as one or more of a tactile keyboard, a display, a touchsensitive display, a microphone, a camera, and any other suitablecomponents that enable a user to control the operation of localcomputing device 100. The implementing software, on the other hand, mayinclude components such as an operating system 150, a contentconsumption application 160, and a data synchronization module 170.Other componentry and functionality not reflected in the schematic blockdiagram of FIG. 1 will be apparent in light of this disclosure, and itwill be appreciated that the present disclosure is not intended to belimited to any particular configuration of hardware and software.

A single user may connect to cloud storage gateway 300 using a varietyof different local computing devices, for example, using a homecomputer, a work computer, and a smartphone. In this case, cloud storagegateway 300 can be configured to replicate the user's data at each ofhis/her devices. Likewise, a single local computing device can be usedby multiple users to connect to cloud storage gateway 300. Thus incertain embodiments local computing device 100 is capable ofpartitioning a resource, such as memory 120, such that it can be sharedby separate users. A user's replicated files can then be stored onhis/her designed memory partition. Regardless whether local computingdevice 100 is used by one or several users, it can be coupled to network500 to allow for communications with other computing devices andresources, such as counter generation module 200 and/or cloud storagegateway 300.

Referring to the hardware components that comprise the example localcomputing device 100 illustrated in FIG. 1, processor 110 can be anysuitable processor, and may include one or more coprocessors orcontrollers, such as an audio processor or a graphics processing unit,to assist in processing operations of local computing device 100. Memory120 can be implemented using any suitable type of digital storage, suchas one or more of a disk drive, a universal serial bus drive, flashmemory, and/or random access memory. In one embodiment memory 120includes a local data repository 122, such as a local file system, intowhich replicated data is stored. Communication module 140 can be anyappropriate network chip or chipset which allows for wired and/orwireless communication via network 500 to one or more of the othercomponents described herein.

In terms of the software components that comprise local computing device100, operating system 150 may comprise any suitable operating system,such as Google Android (Google Inc., Mountain View, Calif.), MicrosoftWindows (Microsoft Corporation, Redmond, Wash.), or Apple OS X (AppleInc., Cupertino, Calif.). As will be appreciated in light of thisdisclosure, the techniques disclosed herein can be implemented withoutregard to the particular operating system provided in conjunction withlocal computing device 100, and therefore may also be implemented usingany suitable existing or subsequently developed platform. Theimplementing software may also include content consumption application160, which can be configured to provide a user interface 162 thatfacilitates interaction with content, such as the data stored in localdata repository 122, or the remotely-stored data managed by cloudstorage gateway 300. For example, in certain embodiments contentconsumption application 160 includes one or more of a web browser, aword processor, a database interface, a digital image editingapplication, a multimedia player, and a document management system.Local computing device 100 may be configured to implement a wide rangeof other content consumption functionality in other embodiments,including content consumption functionality which is remotelyprovisioned via network 500.

Still referring to the example embodiment illustrated in FIG. 1, localcomputing device 100 further includes data synchronization module 170.In one implementation, data synchronization module 170 is configured tosend a request to cloud storage gateway 300 for data synchronizationaccording to a predetermined schedule, for example, once every fiveminutes, once every fifteen minutes, once every thirty minutes, or onceevery hour. Other synchronization intervals can be used in otherimplementations. In an alternative embodiment, data synchronizationmodule 170 is configured to request data synchronization in response toa command received from a user of local computing device 100. Regardlessof how synchronization is triggered, data synchronization module 170 isconfigured to store and report to cloud storage gateway 300 a read state172 that indicates an index of a first data record that is to berequested upon data synchronization. Read state 172 can thus beunderstood as a cursor position from which available data records areread. In implementations wherein cloud storage gateway 300 triggers datasynchronization, data synchronization module 170 can be configured torespond to a request from cloud storage gateway 300 by transmitting readstate 172. Either way, read state 172 enables cloud storage gateway 300to obtain the relevant information from the journal, thereby commencingthe data synchronization process. Data synchronization module 170 isalso optionally configured to receive replicated data from cloud storagegateway 300 and store such data in local data repository 122. If anunavailable data record is encountered, the counter index associatedwith such record can be stored as read state 172 which will serve as thestarting point for a future data replication operation, as will bedescribed in turn. In the example embodiment that is schematicallyillustrated in FIG. 1, read state 172 is represented by the index valuex. In applications where data synchronization involves replicating datathat is stored in a cloud-based storage resource to local computingdevice 100, the terms “data replication” and “data synchronization” canbe used interchangeably.

Counter generation module 200 is configured to provide a source forsequentially increasing counter indices, each of which is associatedwith a creation timestamp. To this end, counter generation module 200includes a counter 210 capable of generating the sequential indices, anda log 220 that comprises a data structure configured to store theindices and the corresponding timestamps for a plurality of users.Counter generation module 200 can be configured to generate new counterindices in response to a request from cloud storage gateway 300, forexample as a result of cloud storage gateway receiving instructions tostore a new data record. In certain embodiments counter generationmodule 200 is configured to maintain separate counter indices andtimestamps for separate users thus enabling cloud storage gateway 300 tomaintain separate journals for separate users. In such embodiments log220 is associated with a token or other metadata that identifies aparticular user. Counter generation module 200 is in communication withcloud storage gateway 300 via network 500. In an alternative embodiment,the functionality associated with counter generation module 200 isintegrated into cloud storage gateway 300.

Referring still to the example data replication system 1000 illustratedin FIG. 1, certain implementations of cloud storage gateway 300 includeone or more software modules configured to implement certain of thefunctionalities disclosed herein, as well as hardware capable ofenabling such implementation. Examples of such implementing softwareinclude a cloud storage administration module 310, a journaladministration module 320, and a journal 340, while examples of suchenabling hardware include a communication module 330 and a plurality ofstorage devices that comprise cloud storage 350.

Cloud storage administration module 310 is configured to manageinteractions with cloud storage 350, including determining whether afull synchronization condition exists, generating new data records to bestored in cloud storage 350, and reading existing data records fromcloud storage 350. Cloud storage administration module 310 also includeslogic for detecting gaps in a sequence of indexed data records stored incloud storage 350, as well as for evaluating the aging of detected gaps.Such determinations enable cloud data replication system 1000 todetermine when it would be appropriate to perform a fullsynchronization, for example due to failure of a storage device orfailure of a data write operation.

Journal administration module 320 is configured to manage journal 340.For example, in certain embodiments journal administration module 320requests new counter indices from counter generation module 200 andupdates journal 340 to include the new counter indices once data recordsare successfully stored in cloud storage 350. Thus in such embodimentsjournal 340 comprises a data structure, also referred to herein as a“journal record”, that includes not only the received index andtimestamp, but also a network address identifying the location where theindexed data record was stored in cloud storage 350. As a result, eachdata record stored in cloud storage 350 is uniquely addressable based on(a) the sequential counter index that is received from countergeneration module 200 and listed in journal 340, and optionally furtherbased on (b) a user token. A given data record can therefore beaddressed by network address information extracted from journal 340.Journal 340 thus provides an ordered listing for the data that aparticular user has stored in cloud storage 350. And when read from readstate 172 stored by data synchronization module 170, journal 340provides a list of updates that should be sent to local computing device100 to maintain synchronization of the local and cloud file systems.This allows the data records stored in cloud storage 350 to be retrievedand replicated in an ordered and consistent fashion.

A journal record can be understood as being immutable in the sense thatonce created, it memorializes a particular data record update. Morespecifically, updating a data record in cloud storage 350, either bymodifying its content or adding a new version, will result in a newjournal record corresponding to that update. Thus, when a data record isupdated several times, several journal records corresponding to theseupdates will be generated. Data synchronization module 170 at localcomputing device 100 interprets these journal records to synchronize theupdates, as disclosed herein. Even where a user wishes to replicate thestored data on multiple local computing devices, for example on a homecomputer, a work computer, and a smartphone, the same journal 340 can beused as a basis for extracting the correct data for replication. Thesequential indices stored in journal 340 ensure that each data recordupdate identified in the journal records is read once during a datareplication operation for a given user. Where cloud storage 350 includesdata associated with multiple users, as will usually be the case,journal administration module 320 can be configured to manage a separatejournal for each of such multiple users. This is because, in principle,each user will wish to replicate a different collection of data fromcloud storage 350. In this multiuser scenario, several different localcomputing devices, each of which is used by a different user, mayreplicate the same shared data record.

Since a particular user may wish to replicate both private data recordsand shared data records, read state 172 optionally comprises multipleread state indices, each of which corresponds to a particular journal.One journal may be configured to record manipulations that affect theparticular user's private data. Each of one or more additional journalsmay be configured to record manipulations that affect shared data thatthe particular user is authorized to access. In particular, when aresource is initially configured as a shared resource, a separatejournal which can be read by all collaborating users is established.Thus local computing device 100 will often read several journals todetermine which data records should be replicated.

With respect to the hardware that enables the foregoing functionality,communication module 330 can be any appropriate network chip or chipsetwhich allows for wired and/or wireless communication via network 500 toone or more of the other components described herein. Cloud storage 350comprises the hardware that is used to store the data managed by cloudstorage gateway 300. In one specific implementation, cloud storage 350comprises a plurality of geographically distributed storage devices 350a, 350 b, 350 c, 350 d, 350 e that use any suitable technology forstoring large quantities of digital data. Examples of such technologiesinclude file servers that use semiconductor storage technology (such asdynamic random access memory or flash memory), magnetic hard discstorage technology, and/or optical disc storage technology. As will beappreciated in light of this disclosure, the techniques disclosed hereincan be implemented without regard to the particular storage technologyused to implement cloud storage 350, and therefore may also beimplemented using any suitable existing or subsequently developedstorage technology. Likewise, while only five storage devices areillustrated in FIG. 1, in general cloud storage 350 will often comprisetens, hundreds, thousands, or more storage devices. Many cloud-basedstorage resources introduce a degree of redundancy into the data storagescheme, and thus a given data record may be stored on a plurality of thestorage devices.

The embodiments disclosed herein can be implemented in various forms ofhardware, software, firmware, or special purpose processors. Forexample, in one embodiment a non-transitory computer readable medium hasinstructions encoded thereon that, when executed by one or moreprocessors, cause one or more of the data storage and replicationmethodologies disclosed herein to be implemented. The instructions canbe encoded using one or more suitable programming languages, such as C,C++, object-oriented C, JavaScript, Visual Basic .NET, BASIC, oralternatively, using custom or proprietary instruction sets. Suchinstructions can be provided in the form of one or more computersoftware applications or applets that are tangibly embodied on a memorydevice, and that can be executed by a computer having any suitablearchitecture. In one embodiment the system can be hosted on a givenwebsite and implemented using JavaScript or another suitablebrowser-based technology.

The functionalities disclosed herein can optionally be incorporated intoa variety of different software applications, such as file managementsystems, document management systems, cloud storage desktopapplications, and operating systems. For example, a document managementsystem can be configured to automatically replicate a user's cloud-basedlibrary of documents in a local file system, thereby providing the userwith full access to his/her library when disconnected from the documentmanagement system. The computer software applications disclosed hereinmay include a number of different modules, sub-modules, or othercomponents of distinct functionality, and can provide information to, orreceive information from, still other components and services. Thesemodules can be used, for example, to communicate with peripheralhardware components, integrated hardware components, networked storageresources, or other external components and/or resources. Moregenerally, other components and functionality not reflected in theillustrations will be apparent in light of this disclosure, and it willbe appreciated that the present disclosure is not intended to be limitedto any particular hardware or software configuration. Thus in otherembodiments the components illustrated in FIG. 1 may compriseadditional, fewer, or alternative subcomponents.

The aforementioned non-transitory computer readable medium may be anysuitable medium for storing digital information, such as a hard drive, aserver, a flash memory, or random access memory. In alternativeembodiments, the computer and modules disclosed herein can beimplemented with hardware, including gate level logic such as afield-programmable gate array, or alternatively, a purpose-builtsemiconductor such as an application-specific integrated circuit. Stillother embodiments may be implemented with a microcontroller having anumber of input and output ports for receiving and transmitting data,respectively, and a number of embedded routines for carrying out thevarious functionalities disclosed herein. It will be apparent that anysuitable combination of hardware, software, and firmware can be used,and that the present disclosure is not intended to be limited to anyparticular system architecture. As used in this disclosure, the term“non-transitory” excludes transitory forms of signal transmission.

Methodology

FIGS. 2A and 2B comprise a flowchart illustrating an example datastorage method 2000 that maintains sequential counter log 220 having acounter index and a timestamp for each of a plurality of users. Theentries in the counter log correspond to journal records that, in turn,correspond to updates to data records that are stored in a cloud-basedstorage resource that is managed by cloud storage gateway 300. FIGS. 3Athrough 3D comprise a flowchart illustrating an example data replicationmethod 3000 that allows local computing device 100 to replicate datastored in a cloud-based storage resource that is managed by, forexample, cloud storage gateway 300. As can be seen, data storage method2000 and data replication method 3000 each include a number of phasesand sub-processes, the sequence of which may vary from one embodiment toanother. However, when considered in the aggregate, these phases andsub-processes form a complete data management process that is responsiveto user commands and/or detected conditions in accordance with certainof the embodiments disclosed herein. These methodologies can beimplemented, for example, using the system architecture illustrated inFIG. 1. However other system architectures can be used in otherembodiments, as will be apparent in light of this disclosure. To thisend, the correlation of the various functionalities shown in FIGS. 2Aand 2B, as well as in FIGS. 3A through 3D, is not intended to imply anystructural and/or use limitations. Rather, other embodiments may includevarying degrees of integration where multiple functionalities areperformed by one system or by separate systems. For instance, in analternative embodiment the functionality associated with countergeneration module 200 can be integrated into cloud storage gateway 300.Thus other embodiments may have fewer or more modules and/or sub-modulesdepending on the granularity of implementation. Numerous variations andalternative configurations will be apparent in light of this disclosure.

In one implementation, example data storage method 2000 commences withthe cloud storage communication module 330 receiving data. See referencenumeral 2110 in FIG. 2A. In many cases communication module 330 willreceive the data from local computing device 100, although in some casesthe data may be received from a different component on behalf of a userof local computing device 100. For example, an email server can beconfigured to forward data that is received at a particular emailaddress to cloud storage gateway 300 with reference to a particularuser's cloud storage account. Regardless of how it is received, journaladministration module 320 is configured to request a new counter indexfrom counter generation module 200 upon receipt of the data. Seereference numeral 2120 in FIG. 2A. In certain implementations therequest sent to counter generation module 200 includes a token or othermetadata identifying the user associated with the received data, therebyenabling counter generation module 200 to create a counter index that issequential to previously generated counter indices for that particularuser. In response to the request, counter generation module 200generates a new counter index and record timestamp, and updates log 220accordingly. See reference numeral 2130 in FIG. 2A. The record timestampcorresponds to the time at which the new counter index was generated.Log 220 is updated to reflect the new counter index, the correspondingrecord timestamp, and a user identification associated with these newparameters. In particular, in implementations where cloud storagegateway 300 manages data associated with multiple users, countergeneration module 200 can be configured to maintain separate log entriesfor separate users. In one implementation the new parameters andgenerated and log 220 is updated atomically to ensure that the newcounter value is unique. The new counter index and corresponding recordtimestamp are sent to cloud storage gateway 300. See reference numeral2140 in FIG. 2A.

Cloud storage administration module 310 generates a new data recordcontaining the received data in cloud storage 350. See reference numeral2150 in FIG. 2A. In some implementations the new data record can bestored redundantly such that it exists at more than one of the pluralityof storage devices 350 a, 350 b, 350 c, 350 d, 350 e that comprise cloudstorage 350. Cloud storage administration module 310 is optionallyconfigured to determine whether the new data record was successfullygenerated. See reference numeral 2210 in FIG. 2B. A number of factorsmay result in failure to generate the new data record, including anaccess conflict caused by a concurrent process or a hardware failure. Ifthe new data record is not successfully generated, another attempt tostore the new data record in cloud storage 350 can be made.Alternatively, the new data record generation process can be terminatedin response to the write failure. In a modified embodiment, the new datarecord generation process is terminated only after a predeterminednumber of storage attempts have failed. If the new data record issuccessfully generated, journal administration module 320 is configuredto update journal 340 to add a new journal record that includes the newcounter index, the corresponding record timestamp, and one or morestorage addresses corresponding to the cloud storage location orlocations where the new data record was stored. See reference numeral2220 in FIG. 2B. Once journal 340 has been updated, data storage method2000 can be understood as having been completed. However, data storagemethod 2000 can be repeated in response to receipt of additional data tobe stored in cloud storage 350.

As data storage method 2000 continues to operate in response to ongoingdata acquisition, journal 340 maintained at cloud storage gateway 300will continue to grow. In implementations where cloud storage gateway300 manages data associated with multiple users, journal administrationmodule 320 can be configured to maintain separate journals for separateusers. At some point data replication method 3000 will be initiated toreplicate a particular user's data from cloud storage 350 to localcomputing device 100 associated with that user. Data replication method3000 can be initiated in response to a variety of predeterminedcriteria. For example, in one implementation data replication method3000 is triggered when cloud storage gateway 300 detects that athreshold quantity of new data records have been identified in journal340. In another implementation, data replication method 3000 istriggered when local computing device 100 detects that a datareplication operation has not occurred within a specific threshold timeperiod. In still other implementations, a combination of differentconditions are used to determine when data replication method 3000should commence. A wide range of other triggers can be used in otherembodiments, and it will be appreciated that the various datareplication methods disclosed herein can operate without regard to thedetails of the particular triggering event.

In one implementation, example data replication method 3000 commenceswith obtaining read state 172 from data synchronization module 170. Forpurposes of this disclosure, the obtained read state, which comprises asequential counter index value, will be referred to herein as x. Seereference numeral 3110 in FIG. 3A. Data synchronization module 170 isconfigured to request data synchronization from cloud storage gateway300 beginning at the xth data record identified in journal 340, whichalso corresponds to the xth journal record. See reference numeral 3120in FIG. 3A.

Upon receipt of the read state 172, cloud storage administration module310 can be configured to determine whether a full synchronizationcondition exists. See reference numeral 3130 in FIG. 3A. Examples offull synchronization conditions include existence of a large quantity ofdata records that should be replicated, or a long time period since thelast full synchronization was performed. In situations such as these, itis often more efficient to perform a full synchronization rather than tosequentially check the availability of individual data records, as willbe described in turn. For example, in one implementation a fullsynchronization condition is considered to exist where the gap betweenread state 172 and the largest counter index stored in journal 340exceeds 3000 indices. In another implementation, a full synchronizationcondition is considered to exist where the most recent fullsynchronization was performed more than twelve hours ago. One or moreother full synchronization conditions can be implemented in otherembodiments. Where a full synchronization condition is found to exist,cloud storage administration module 310 can be configured to perform thefull synchronization. See reference numeral 3140 in FIG. 3A. In certainembodiments the full synchronization can be understood as comprising aprocess wherein a listing of all cloud storage data records are sent tolocal computing device 100. Local computing device can then determinewhich data records should be downloaded or uploaded. While a fullsynchronization generally consumes additional time and resources ascompared to an incremental record-by-record data replication process,the burden this imposes on the user is mitigated by the fact that fullsynchronizations are performed relatively infrequently, for example inresponse to the aforementioned full synchronization conditions. Once thefull synchronization is performed, the user's cloud-based data isreplicated on local computing device 100, and therefore data replicationmethod 3000 can be understood as having been completed.

If it is determined that a full synchronization condition does notexist, cloud storage administration module 310 can be configured todetermine whether the xth journal record, which corresponds to readstate 172, exists. See reference numeral 3210 in FIG. 3B. If the xthjournal record exists, it can be queued for synchronization. Seereference numeral 3220 in FIG. 3B. This can be accomplished by eithercopying the corresponding journal record to a memory cache hosted bycloud storage gateway 300, or alternatively, by queuing the networkaddress itself. Read state x is then incremented. See reference numeral3230 in FIG. 3B. It is then once again determined whether xth journalrecord exists.

As the read state x continues to increment, eventually a nonexistentjournal record will be encountered. Where this is the case, cloudstorage administration module 310 can be configured to determine whetherany subsequent journal records exist. See reference numeral 3240 in FIG.3B. Such a journal record would be associated with a counter indexgreater than or equal to (x+1). If such a journal record is available,this means that a gap exists at counter index x in the journal records.In this case, the data record corresponding to the (x+1)th journalrecord should not yet be queued for replication at local computingdevice 100 since doing so would cause intervening data records to belost. Rather, cloud storage administration module 310 can be configuredto evaluate a gap duration between the current time and the timestampfor the next available journal record. See reference numeral 3250 inFIG. 3B. This effectively measures the aging of the missing journalrecord or records. It can then be determined whether the evaluated gapduration exceeds a predetermined threshold. See reference numeral 3260in FIG. 3B. If not, cloud storage administration module 310 can beconfigured to send the queued data records to the local computingdevice, as will be described in turn. However, if the evaluated gapduration does exceed the predetermined threshold, an inconsistency injournal 340 can be assumed, for example due to a server crash or afailed data write operation. In this case, a full synchronization isperformed. In one implementation the predetermined threshold used todetermine whether or not to perform a full synchronization isapproximately five minutes.

If no subsequent journal record exists, it is possible that journalrecord x should be the last journal record indexed in journal 340, butdoes not exist due to a failed write operation or the like. This wouldmake it impossible to detect any gap, as described above. Therefore, todetermine whether this is the case, cloud storage administration module310 is configured to obtain the last available counter index for theuser associated with the data replication operation from log 220maintained by counter generation module 200 (ID_(log)). See referencenumeral 3310 in FIG. 3C. Cloud storage administration module 310 is alsoconfigured to obtain the counter index corresponding to the xth journalrecord maintained by cloud storage gateway 300 (ID_(journal)). Seereference numeral 3320 in FIG. 3C. It can then be determined whetherthese two counter indices are equal, that is, whetherID_(log)=ID_(journal). See reference numeral 3330 in FIG. 3C.

If the two counter indices are in fact equal, it can be assumed that the(x−1)th journal record was the last indexed journal record, and that nojournal records are missing. In this case cloud storage communicationmodule 330 can be configured to send a list of the queued journalrecords to local computing device 100. See reference numeral 3410 inFIG. 3D. Because the next data replication operation should commence atread state x, cloud storage communication module 330 is also configuredto send the current read state x to local computing device 100. Seereference numeral 3420 in FIG. 3D. Data synchronization module 170 isconfigured to retrieve data records identified list of queued journalrecords, and store the retrieved data records in local data repository122. See reference numeral 3430 in FIG. 3D. In certain embodiments allof the queued data records are transmitted to local computing device 100in one batch, while in alternative embodiments queued data records aretransmitted to local computing device 100 in blocks based on a maximumpage size. Data synchronization module 170 is also configured to storethe received current read state x, thus enabling a subsequent datareplication operation to commence at the correct journal record. Seereference numeral 3440 in FIG. 3D. Once the replicated data records andthe read state are saved by local computing device 100, data replicationmethod 300 can be understood as having been completed.

If the two counter indices ID_(log) and ID_(journal) are not equal, itcan be assumed that at least the xth journal record is missing. In thiscase cloud storage administration module 310 can be configured toevaluate a gap duration between the current time and the last availabletimestamp for the user associated with the data replication operationfrom log 220 maintained by counter generation module 200 (TS_(log)). Seereference numeral 3340 in FIG. 3C. This effectively measures the agingof the missing journal record. It can then be determined whether theevaluated gap duration exceeds a predetermined threshold. See referencenumeral 3350 in FIG. 3C. If not, cloud storage administration module 310can be configured to send a list of the queued journal records to localcomputing device 100, as described previously. However, if the evaluatedgap duration does exceed the predetermined threshold, an inconsistencyin journal 340 can be assumed, for example due to a server crash or afailed data write operation. In this case, a full synchronization isperformed. In one implementation the predetermined threshold used todetermine whether or not to perform a full synchronization isapproximately five minutes.

Conclusion

Numerous variations and configurations will be apparent in light of thisdisclosure. For instance one example embodiment provides a method forreplicating data records stored in a cloud-based storage resource at alocal computing device. The method comprises receiving a read statecounter index from the local computing device. The method furthercomprises identifying, with reference to a journal, a plurality ofjournal records. Each of the journal records is associated with acounter index that forms a sequence starting with the read state counterindex. Each of the journal records corresponds to a data record storedin the cloud-based storage resource. The method further comprisesidentifying an unavailable journal record that interrupts the sequenceand that is associated with an unavailable counter index. The methodfurther comprises transmitting a plurality of data records to the localcomputing device. The transmitted plurality of data records correspondto the identified plurality of journal records. The method furthercomprises transmitting the unavailable counter index to the localcomputing device. In some cases the unavailable counter index isassociated with a data record that is not available to be retrieved fromthe cloud-based storage resource. In some cases the unavailable counterindex is transmitted with instructions to replace the read state counterindex with the unavailable counter index. In some cases the plurality oftransmitted data records are transmitted to the local computing devicein batches corresponding to a maximum page size. In some cases themethod further comprises queueing the plurality of transmitted datarecords in a cache before transmitting them to the local computingdevice. In some cases identifying the plurality of journal recordsfurther comprises (a) identifying a subsequent journal record associatedwith a counter index that is greater than the unavailable counter index,such that a gap exists in the sequence; and (b) determining an age ofthe gap. In some cases identifying the plurality of journal recordsfurther comprises (a) identifying a subsequent journal record associatedwith a counter index that is greater than the unavailable counter index,such that a gap exists in the sequence; and (b) determining a differencebetween a timestamp associated with the subsequent journal record and acurrent time. In some cases the cloud-based storage resource comprises aplurality of geographically distributed storage devices. In some casesthe method further comprises comparing the unavailable counter indexwith a last available counter index maintained by a counter generationmodule. In some cases the method further comprises (a) identifying asubsequent journal record associated with a counter index that isgreater than the unavailable counter index, such that a gap exists inthe sequence; and (b) invoking a full synchronization procedure inresponse to determining that the gap corresponds to a quantity ofcounter indices that exceeds a full synchronization threshold. In somecases the journal includes a record timestamp associated with each ofthe counter indices, the record timestamp corresponding to a time atwhich the associated counter index was generated.

Another example embodiment provides a data replication system thatcomprises a counter generation module. The counter generation modulecomprises a log entry that correlates a user, a counter index, and acreation timestamp. The system further comprises a cloud storagegateway. The cloud storage gateway comprises a plurality of cloudstorage devices that form a cloud storage resource, and thatcollectively store a plurality of data records. The cloud storagegateway further comprises a journal that comprises a plurality ofjournal records. Each of the journal records correlates (a) a networkaddress that identifies where a particular data record is stored in thecloud storage resource with (b) a particular counter index associatedwith a particular operation having been performed on the particular datarecord. The cloud storage gateway further comprises a cloud storageadministration module configured to generate a list of journal recordsthat corresponds to a plurality of operations recorded in the journal.The list comprises a continuous sequence of counter indices thatterminates before the counter index included in the counter generationmodule log entry. In some cases the system further comprises acommunication interface configured transmit the list of journal recordsto a client computing device. In some cases the log entry includes atoken that identifies the user. In some cases the cloud storage gatewayfurther comprises a journal administration module configured to requesta new sequential counter index from the counter generation module inresponse to receipt of data that is to be stored in the cloud storageresource. In some cases the cloud storage administration module isfurther configured to identify a nonsequential journal record associatedwith a counter index that is greater than the counter index included inthe counter generation module log entry. In some cases each of thejournal records further correlates the network address with a particularcreation timestamp corresponding to a time that the particular counterindex was generated by the counter generation module.

Another example embodiment provides a computer program product that,when executed by one or more processors, causes a data storage processto be carried out. The process comprises receiving new data to be storedin a cloud-based storage resource. The process further comprises, inresponse to receiving the new data, generating a new journal record thatcomprises a new counter index and a timestamp. The new counter index isextracted from a user-specific log maintained by a counter generationmodule. The process further comprises saving an incremented counterindex in the user-specific log. The process further comprises saving thenew data in the cloud-based storage resource at a location identified bya network address. The new journal record correlates the new counterindex with the network address. The new counter index is a sequentialaddition to an existing plurality of counter indices stored in acorresponding plurality of existing journal records that collectivelyrepresent a sequence of data modification operations performed on datastored in the cloud-based storage resource. In some cases the timestampcorresponds to a time at which the new data was saved in the cloud-basedstorage resource. In some cases (a) the new data is saved in thecloud-based storage resource at a plurality of locations identified by acorresponding plurality of network addresses; and (b) the new journalrecord correlates the new counter index with the plurality of networkaddresses. In some cases the new data is received by a cloud storagegateway that is in communication with the counter generation module.

The foregoing detailed description has been presented for the purposesof illustration and description. It is not intended to be exhaustive orto limit the invention to the particular disclosed embodiments. Manymodifications and variations are possible in light of this disclosure.Thus it is intended that the scope of the invention be limited not bythis detailed description, but rather by the claims appended hereto.

What is claimed is:
 1. A method for replicating data records stored in acloud-based storage resource at a local computing device, the methodcomprising: receiving a read state counter index from the localcomputing device; identifying, with reference to a journal, a pluralityof journal records, each of which (a) is associated with a counter indexthat forms a sequence starting with the read state counter index, and(b) corresponds to a data record stored in the cloud-based storageresource; identifying an unavailable journal record that interrupts thesequence and that is associated with an unavailable counter index;transmitting a plurality of data records to the local computing device,wherein the transmitted plurality of data records correspond to theidentified plurality of journal records; and transmitting theunavailable counter index to the local computing device.
 2. The methodof claim 1, wherein the unavailable counter index is transmitted withinstructions to replace the read state counter index with theunavailable counter index.
 3. The method of claim 1, wherein theplurality of transmitted data records are transmitted to the localcomputing device in batches corresponding to a maximum page size.
 4. Themethod of claim 1, further comprising queueing the plurality oftransmitted data records in a cache before transmitting them to thelocal computing device.
 5. The method of claim 1, wherein identifyingthe plurality of journal records further comprises: identifying asubsequent journal record associated with a counter index that isgreater than the unavailable counter index, such that a gap exists inthe sequence; and determining an age of the gap.
 6. The method of claim1, wherein identifying the plurality of journal records furthercomprises: identifying a subsequent journal record associated with acounter index that is greater than the unavailable counter index, suchthat a gap exists in the sequence; and determining a difference betweena timestamp associated with the subsequent journal record and a currenttime.
 7. The method of claim 1, wherein the cloud-based storage resourcecomprises a plurality of geographically distributed storage devices. 8.The method of claim 1, further comprising comparing the unavailablecounter index with a last available counter index maintained by acounter generation module.
 9. The method of claim 1, further comprising:identifying a subsequent journal record associated with a counter indexthat is greater than the unavailable counter index, such that a gapexists in the sequence; and invoking a full synchronization procedure inresponse to determining that the gap corresponds to a quantity ofcounter indices that exceeds a full synchronization threshold.
 10. Themethod of claim 1, wherein the journal includes a record timestampassociated with each of the counter indices, the record timestampcorresponding to a time at which the associated counter index wasgenerated.
 11. A data replication system comprising: a countergeneration module comprising a log entry that correlates a user, acounter index, and a creation timestamp; and a cloud storage gatewaythat comprises a plurality of cloud storage devices that form a cloudstorage resource, and that collectively store a plurality of datarecords, a journal that comprises a plurality of journal records, eachof which correlates (a) a network address that identifies where aparticular data record is stored in the cloud storage resource with (b)a particular counter index associated with a particular operation havingbeen performed on the particular data record, and a cloud storageadministration module configured to generate a list of journal recordsthat corresponds to a plurality of operations recorded in the journal,the list comprising a continuous sequence of counter indices thatterminates before the counter index included in the counter generationmodule log entry.
 12. The data replication system of claim 11, furthercomprising a communication interface configured transmit the list ofjournal records to a client computing device.
 13. The data replicationsystem of claim 11, wherein the log entry includes a token thatidentifies the user.
 14. The data replication system of claim 11,wherein the cloud storage gateway further comprises a journaladministration module configured to request a new sequential counterindex from the counter generation module in response to receipt of datathat is to be stored in the cloud storage resource.
 15. The datareplication system of claim 11, wherein the cloud storage administrationmodule is further configured to identify a nonsequential journal recordassociated with a counter index that is greater than the counter indexincluded in the counter generation module log entry.
 16. The datareplication system of claim 11, wherein each of the journal recordsfurther correlates the network address with a particular creationtimestamp corresponding to a time that the particular counter index wasgenerated by the counter generation module.
 17. A computer programproduct that, when executed by one or more processors, causes a datastorage process to be carried out, the data storage process comprising:receiving new data to be stored in a cloud-based storage resource; inresponse to receiving the new data, generating a new journal record thatcomprises a new counter index and a timestamp, wherein the new counterindex is extracted from a user-specific log maintained by a countergeneration module; saving an incremented counter index in theuser-specific log; and saving the new data in the cloud-based storageresource at a location identified by a network address; wherein the newjournal record correlates the new counter index with the networkaddress, and wherein the new counter index is a sequential addition toan existing plurality of counter indices stored in a correspondingplurality of existing journal records that collectively represent asequence of data modification operations performed on data stored in thecloud-based storage resource.
 18. The computer program product of claim17, wherein the timestamp corresponds to a time at which the new datawas saved in the cloud-based storage resource.
 19. The computer programproduct of claim 17, wherein: the new data is saved in the cloud-basedstorage resource at a plurality of locations identified by acorresponding plurality of network addresses; and the new journal recordcorrelates the new counter index with the plurality of networkaddresses.
 20. The computer program product of claim 17, wherein the newdata is received by a cloud storage gateway that is in communicationwith the counter generation module.